Light fixture as an access point in a communication network

ABSTRACT

A light fixture is described herein. The light fixture can include a housing having at least one wall that forms a cavity. The light fixture can also include a controller configured to control and communicate with at least one sensor located outside the housing. The light fixture can further include at least one light fixture component coupled to the controller and disposed within the cavity of the housing, where the controller further controls the at least one light fixture component.

TECHNICAL FIELD

The present disclosure relates generally to light fixtures in a wirelessnetwork, and more particularly to systems, methods, and devices forlight fixtures used as an access point in a communication network.

BACKGROUND

In wireless networks, there are nodes and one or more access points thatcommunicate with each other. The node sends and receives data through anaccess point, and the access point sends the data to and receives otherdata from a controller within the wireless network. Data is sent andreceived within the communication network using a communicationprotocol.

SUMMARY

In general, in one aspect, the disclosure relates to a light fixture.The light fixture can include a housing comprising at least one wallthat forms a cavity. The light fixture can also include a controllerconfigured to control and communicate with at least one sensor locatedoutside the housing. The light fixture can further include at least onelight fixture component coupled to the controller and disposed withinthe cavity of the housing, where the controller further controls the atleast one light fixture component.

In another aspect, the disclosure can generally relate to a controllerof a light fixture. The controller can include memory comprising aplurality of instructions. The controller can also include a controlengine coupled to the memory, where the controller is configured to sendand receive communication signals with at least one sensor based on theplurality of instructions, where the at least one sensor is external tothe light fixture. The controller can further include a communicationmodule coupled to the control engine, where the communication module isconfigured to transmit the communication signals between the controlengine and the at least one sensor. The control module can transmit thecommunication signals using at least one time-synchronized communicationprotocol.

In yet another aspect, the disclosure can generally relate to anelectrical system. The electrical system can include at least onesensor, and a light fixture communicably coupled to the at least onesensor. The light fixture of the electrical system can include a housingcomprising at least one wall that forms a cavity. The light fixture ofthe electrical system can also include a controller that controls andcommunicates with the at least one sensor. The light fixture of theelectrical system can further include at least one light fixturecomponent coupled to the controller and disposed within the cavity ofthe housing, where the controller further controls the at least onelight fixture component. The at least one sensor can be located outsidethe housing of the light fixture.

These and other aspects, objects, features, and embodiments will beapparent from the following description and the appended claims.

BRIEF DESCRIPTION OF THE DRAWINGS

The drawings illustrate only example embodiments and are therefore notto be considered limiting in scope, as the example embodiments may admitto other equally effective embodiments. The elements and features shownin the drawings are not necessarily to scale, emphasis instead beingplaced upon clearly illustrating the principles of the exampleembodiments. Additionally, certain dimensions or positionings may beexaggerated to help visually convey such principles. In the drawings,reference numerals designate like or corresponding, but not necessarilyidentical, elements.

FIG. 1 shows a system diagram of a lighting system that includes a lightfixture in accordance with certain example embodiments.

FIG. 2 shows a computing device in accordance with certain exampleembodiments.

FIG. 3 shows a system diagram of architecture for a networkcommunication system in accordance with certain example embodiments.

FIGS. 4 and 5 show system diagrams of a network communication systemcurrently known in the art.

FIGS. 6 and 7 show a system diagram of a network communication system inaccordance with certain example embodiments.

FIG. 8 shows network data frame architecture in accordance with certainexample embodiments.

DETAILED DESCRIPTION

In general, example embodiments provide systems, methods, and devicesfor light fixtures used as an access point in a communication network.Example light fixtures used as an access point in a communicationnetwork provide a number of benefits. Such benefits can include, but arenot limited to, increased flexibility of the arrangement of sensors in acommunication network, reduced power consumption, improved communicationefficiency, ease of maintenance, and compliance with industry standardsthat apply to electrical enclosures located in certain environments.

In some cases, the example embodiments discussed herein can be used inany type of hazardous environment, including but not limited to anairplane hangar, a drilling rig (as for oil, gas, or water), aproduction rig (as for oil or gas), a refinery, a chemical plant, apower plant, a mining operation, a wastewater treatment facility, and asteel mill. A user may be any person that interacts with example lightfixtures used as an access point in a communication network. Examples ofa user may include, but are not limited to, an engineer, an electrician,an instrumentation and controls technician, a mechanic, an operator, aconsultant, a contractor, and a manufacturer's representative.

The example light fixtures used as an access point in a communicationnetwork (or components thereof, including controllers) described hereincan be made of one or more of a number of suitable materials to allowthe light fixture and/or other associated components of a system to meetcertain standards and/or regulations while also maintaining durabilityin light of the one or more conditions under which the light fixturesand/or other associated components of the system can be exposed.Examples of such materials can include, but are not limited to,aluminum, stainless steel, fiberglass, glass, plastic, ceramic, andrubber.

Example light fixtures used as an access point in a communicationnetwork, or portions thereof, described herein can be made from a singlepiece (as from a mold, injection mold, die cast, or extrusion process).In addition, or in the alternative, example light fixtures used as anaccess point in a communication network can be made from multiple piecesthat are mechanically coupled to each other. In such a case, themultiple pieces can be mechanically coupled to each other using one ormore of a number of coupling methods, including but not limited toepoxy, welding, fastening devices, compression fittings, mating threads,and slotted fittings. One or more pieces that are mechanically coupledto each other can be coupled to each other in one or more of a number ofways, including but not limited to fixedly, hingedly, removeably,slidably, and threadably.

In the foregoing figures showing example embodiments of light fixturesused as an access point in a communication network, one or more of thecomponents shown may be omitted, repeated, and/or substituted.Accordingly, example embodiments of light fixtures used as an accesspoint in a communication network should not be considered limited to thespecific arrangements of components shown in any of the figures. Forexample, features shown in one or more figures or described with respectto one embodiment can be applied to another embodiment associated with adifferent figure or description.

As defined herein, an electrical enclosure is any type of cabinet orhousing inside of which is disposed electrical and/or electronicequipment. Such electrical and/or electronic equipment can include, butis not limited to, a control module, a hardware processor, a powermodule (e.g., a battery, a driver, a ballast), a sensor module, a safetybarrier, a sensor, sensor circuitry, a light source, electrical cables,and electrical conductors. Examples of an electrical enclosure caninclude, but are not limited to, a housing for a light fixture, ahousing for a sensor device, an electrical connector, a junction box, amotor control center, a breaker box, an electrical housing, a conduit, acontrol panel, an indicating panel, and a control cabinet.

In certain example embodiments, light fixtures used as an access pointin a communication network are subject to meeting certain standardsand/or requirements. For example, the National Electric Code (NEC), theNational Electrical Manufacturers Association (NEMA), the InternationalElectrotechnical Commission (IEC), the Federal Communication Commission(FCC), and the Institute of Electrical and Electronics Engineers (IEEE)set standards as to electrical enclosures, wiring, and electricalconnections. Use of example embodiments described herein meet (and/orallow a corresponding device to meet) such standards when required. Insome (e.g., PV solar) applications, additional standards particular tothat application may be met by the electrical enclosures describedherein.

If a component of a figure is described but not expressly shown orlabeled in that figure, the label used for a corresponding component inanother figure can be inferred to that component. Conversely, if acomponent in a figure is labeled but not described, the description forsuch component can be substantially the same as the description for thecorresponding component in another figure. The numbering scheme for thevarious components in the figures herein is such that each component isa three digit number and corresponding components in other figures havethe identical last two digits.

Example embodiments of light fixtures used as an access point in acommunication network will be described more fully hereinafter withreference to the accompanying drawings, in which example embodiments oflight fixtures used as an access point in a communication network areshown. Light fixtures used as an access point in a communication networkmay, however, be embodied in many different forms and should not beconstrued as limited to the example embodiments set forth herein.Rather, these example embodiments are provided so that this disclosurewill be thorough and complete, and will fully convey the scope of lightfixtures used as an access point in a communication network to those ofordinary skill in the art. Like, but not necessarily the same, elements(also sometimes called components) in the various figures are denoted bylike reference numerals for consistency.

Terms such as “first”, “second”, and “within” are used merely todistinguish one component (or part of a component or state of acomponent) from another. Such terms are not meant to denote a preferenceor a particular orientation, and are not meant to limit embodiments oflight fixtures used as an access point in a communication network. Inthe following detailed description of the example embodiments, numerousspecific details are set forth in order to provide a more thoroughunderstanding of the invention. However, it will be apparent to one ofordinary skill in the art that the invention may be practiced withoutthese specific details. In other instances, well-known features have notbeen described in detail to avoid unnecessarily complicating thedescription.

FIG. 1 shows a system diagram of a lighting system 100 that includes alight fixture 102 in accordance with certain example embodiments. Thelighting system 100 can include one or more sensors 160, a user 150, anetwork manager 180, and a light fixture 102. The light fixture 102 caninclude a controller 104, a power module 140, a number of light fixturecomponents 142, and an optional safety barrier 136. The controller 104can include one or more of a number of components. Such components, caninclude, but are not limited to, a control engine 106, a communicationmodule 108, a timer 110, a power module 112, a storage repository 130, ahardware processor 120, a memory 122, a transceiver 124, an applicationinterface 126, and, optionally, a security module 128. The componentsshown in FIG. 1 are not exhaustive, and in some embodiments, one or moreof the components shown in FIG. 1 may not be included in an examplelight fixture. Any component of the example light fixture 102 can bediscrete or combined with one or more other components of the lightfixture 102.

The user 150 is the same as a user defined above. The user 150 can use auser system (not shown), which may include a display (e.g., a GUI). Theuser 150 interacts with (e.g., sends data to, receives data from) thecontroller 104 of the light fixture 102 via the application interface126 (described below). The user 150 can also interact with a networkmanager 180 and/or one or more of the sensors 160. Interaction betweenthe user 150 and the light fixture 102, the network manager 180, and thesensors 160 is conducted using communication links 105. Eachcommunication link 105 can include wired (e.g., Class 1 electricalcables, Class 2 electrical cables, electrical connectors) and/orwireless (e.g., Wi-Fi, visible light communication, cellular networking,Bluetooth, WirelessHART, ISA100, Power Line Carrier, RS485, DALI)technology. For example, a communication link 105 can be (or include)one or more electrical conductors that are coupled to the housing 103 ofthe light fixture 102 and to a sensor 160. The communication link 105can transmit signals (e.g., power signals, communication signals,control signals, data) between the light fixture 102 and the user 150,the network manager 180, and/or one or more of the sensors 160.

The network manager 180 is a device or component that controls all or aportion of a communication network that includes the controller 104 ofthe light fixture 102 and the sensors 160 that are communicably coupledto the controller 104. The network manager 180 can be substantiallysimilar to the controller 104. Alternatively, the network manager 180can include one or more of a number of features in addition to, oraltered from, the features of the controller 104 described below.

The one or more sensors 160 can be any type of sensing device thatmeasure one or more parameters. Examples of types of sensors 160 caninclude, but are not limited to, a passive infrared sensor, a photocell,a pressure sensor, an air flow monitor, a gas detector, and a resistancetemperature detector. A parameter that can be measured by a sensor 160can include, but is not limited to, motion, an amount of ambient light,occupancy of a space, and an ambient temperature. In some cases, theparameter or parameters measured by a sensor 160 can be used to operateone or more light fixture components 142 of the light fixture 102. Eachsensor 160 can use one or more of a number of communication protocols.

In certain example embodiments, a sensor 160 can include a battery thatis used to provide power, at least in part, to some or all of the restof the sensor 160. When the system 100 (or at least a sensor 160) islocated in a hazardous environment, the sensor 160 can be intrinsicallysafe. As used herein, the term “intrinsically safe” refers to a device(e.g., a sensor described herein) that is placed in a hazardousenvironment. To be intrinsically safe, the device uses a limited amountof electrical energy so that sparks cannot occur from a short circuit orfailures that can cause an explosive atmosphere found in hazardousenvironments to ignite. A safety barrier is commonly used with anintrinsically safe device, where the safety barrier limits the amount ofpower delivered to the sensor or other device to reduce the risk ofexplosion, fire, or other adverse condition that can be caused by highamounts of power in the hazardous environment.

The user 150, the network manager 180, and/or the sensors 160 caninteract with the controller 104 of the light fixture 102 using theapplication interface 126 in accordance with one or more exampleembodiments. Specifically, the application interface 126 of thecontroller 104 receives data (e.g., information, communications,instructions) from and sends data (e.g., information, communications,instructions) to the user 150, the network manager 180, and/or eachsensor 160. The user 150, the network manager 180, and/or each sensor160 can include an interface to receive data from and send data to thecontroller 104 in certain example embodiments. Examples of such aninterface can include, but are not limited to, a graphical userinterface, a touchscreen, an application programming interface, akeyboard, a monitor, a mouse, a web service, a data protocol adapter,some other hardware and/or software, or any suitable combinationthereof.

The controller 104, the user 150, the network manager 180, and/or thesensors 160 can use their own system or share a system in certainexample embodiments. Such a system can be, or contain a form of, anInternet-based or an intranet-based computer system that is capable ofcommunicating with various software. A computer system includes any typeof computing device and/or communication device, including but notlimited to the controller 104. Examples of such a system can include,but are not limited to, a desktop computer with LAN, WAN, Internet orintranet access, a laptop computer with LAN, WAN, Internet or intranetaccess, a smart phone, a server, a server farm, an android device (orequivalent), a tablet, smartphones, and a personal digital assistant(PDA). Such a system can correspond to a computer system as describedbelow with regard to FIG. 2.

Further, as discussed above, such a system can have correspondingsoftware (e.g., user software, sensor software, controller software,network manager software). The software can execute on the same or aseparate device (e.g., a server, mainframe, desktop personal computer(PC), laptop, personal desktop assistant (PDA), television, cable box,satellite box, kiosk, telephone, mobile phone, or other computingdevices) and can be coupled by the communication network (e.g.,Internet, Intranet, Extranet, Local Area Network (LAN), Wide AreaNetwork (WAN), or other network communication methods) and/orcommunication channels, with wire and/or wireless segments according tosome example embodiments. The software of one system can be a part of,or operate separately but in conjunction with, the software of anothersystem within the system 100.

The light fixture 102 can include a housing 103. The housing 103 caninclude at least one wall that forms a cavity 101. In some cases, thehousing can be designed to comply with any applicable standards so thatthe light fixture 102 can be located in a particular environment (e.g.,a hazardous environment). For example, if the light fixture 102 islocated in an explosive environment, the housing 103 can beexplosion-proof. According to applicable industry standards, anexplosion-proof enclosure is an enclosure that is configured to containan explosion that originates inside, or can propagate through, theenclosure.

Continuing with this example, the explosion-proof enclosure isconfigured to allow gases from inside the enclosure to escape acrossjoints of the enclosure and cool as the gases exit the explosion-proofenclosure. The joints are also known as flame paths and exist where twosurfaces meet and provide a path, from inside the explosion-proofenclosure to outside the explosion-proof enclosure, along which one ormore gases may travel. A joint may be a mating of any two or moresurfaces. Each surface may be any type of surface, including but notlimited to a flat surface, a threaded surface, and a serrated surface.

The housing 103 of the light fixture 102 can be used to house one ormore components of the light fixture 102, including one or morecomponents of the controller 104. For example, as shown in FIG. 1, thecontroller 104 (which in this case includes the control engine 106, thecommunication module 108, the timer 110, the power module 112, thestorage repository 130, the hardware processor 120, the memory 122, thetransceiver 124, the application interface 126, and the optionalsecurity module 128), the power module 140, and the light fixturecomponents 142 are disposed in the cavity 101 formed by the housing 103.In alternative embodiments, any one or more of these or other componentsof the light fixture 102 can be disposed on the housing 103 and/orremotely from the housing 103.

The storage repository 130 can be a persistent storage device (or set ofdevices) that stores software and data used to assist the controller 104in communicating with the user 150, the network manager 180, and one ormore sensors 160 within the system 100. In one or more exampleembodiments, the storage repository 130 stores one or more communicationprotocols 132 and sensor data 134. The communication protocols 132 canbe any of a number of protocols that are used to send and/or receivedata between the controller 104 and the user 150, the network manager180, and one or more sensors 160. One or more of the communicationprotocols 132 can be a time-synchronized protocol. Examples of suchtime-synchronized protocols can include, but are not limited to, ahighway addressable remote transducer (HART) protocol, a wirelessHARTprotocol, and an International Society of Automation (ISA) 100 protocol.In this way, one or more of the communication protocols 132 can providea layer of security to the data transferred within the system 100.

Sensor data 134 can be any data associated with each sensor 160 that iscommunicably coupled to the controller 104. Such data can include, butis not limited to, a manufacturer of the sensor 160, a model number ofthe sensor 160, communication capability of a sensor 160, powerrequirements of a sensor 160, and measurements taken by the sensor 160.Examples of a storage repository 130 can include, but are not limitedto, a database (or a number of databases), a file system, a hard drive,flash memory, some other form of solid state data storage, or anysuitable combination thereof. The storage repository 130 can be locatedon multiple physical machines, each storing all or a portion of thecommunication protocols 132 and/or the sensor data 134 according to someexample embodiments. Each storage unit or device can be physicallylocated in the same or in a different geographic location.

The storage repository 130 can be operatively connected to the controlengine 106. In one or more example embodiments, the control engine 106includes functionality to communicate with the user 150, the networkmanager 180, and the sensors 160 in the system 100. More specifically,the control engine 106 sends information to and/or receives informationfrom the storage repository 130 in order to communicate with the user150, the network manager 180, and the sensors 160. As discussed below,the storage repository 130 can also be operatively connected to thecommunication module 108 in certain example embodiments.

In certain example embodiments, the control engine 106 of the controller104 controls the operation of one or more components (e.g., thecommunication module 108, the timer 110, the transceiver 124) of thecontroller 104. For example, the control engine 106 can put thecommunication module 108 in “sleep” mode when there are nocommunications between the controller 104 and another component (e.g., asensor 160, the user 150) in the system 100 or when communicationsbetween the controller 104 and another component in the system 100follow a regular pattern. In such a case, power consumed by thecontroller 104 is conserved by only enabling the communication module108 when the communication module 108 is needed.

As another example, the control engine 106 can direct the timer 110 whento provide a current time, to begin tracking a time period, and/orperform another function within the capability of the timer 110. As yetanother example, the control engine 106 can direct the power module 112to send power signals and/or stop sending power signals to one or moresensors 160 in the system 100. This example provides another instancewhere the control engine 106 can conserve power used by the controller104 and other components of the system 100.

The control engine 106 can provide control, communication, and/or othersimilar signals to the user 150, the network manager 180, and one ormore of the sensors 160. Similarly, the control engine 106 can receivecontrol, communication, and/or other similar signals from the user 150,the network manager 180, and one or more of the sensors 160. The controlengine 106 can control each sensor 160 automatically (for example, basedon one or more algorithms stored in the control engine 106) and/or basedon control, communication, and/or other similar signals received fromanother device through a communication link 105. The control engine 106may include a printed circuit board, upon which the hardware processor120 and/or one or more discrete components of the controller 104 arepositioned.

In certain example embodiments, the control engine 106 can include aninterface that enables the control engine 106 to communicate with one ormore components (e.g., power module 140) of the light fixture 102. Forexample, if the power module 140 of the light fixture 102 operates underIEC Standard 62386, then the power module 140 can include a digitaladdressable lighting interface (DALI). In such a case, the controlengine 106 can also include a DALI to enable communication with thepower module 140 within the light fixture 102. Such an interface canoperate in conjunction with, or independently of, the communicationprotocols 132 used to communicate between the controller 104 and theuser 150, the network manager 180, and the sensors 160.

The control engine 106 (or other components of the controller 104) canalso include one or more hardware and/or software architecturecomponents to perform its functions. Such components can include, butare not limited to, a universal asynchronous receiver/transmitter(UART), a serial peripheral interface (SPI), a direct-attached capacity(DAC) storage device, an analog-to-digital converter, aninter-integrated circuit (I²C), and a pulse width modulator (PWM).

By using the control engine 106 as described herein, the controller 104can serve as an access point in the communication network (e.g., usingthe communication links 105) of the system 100. In other words, while atleast a portion (e.g., the control engine 106) of the controller 104 isalways on, the remainder of the controller 104 and the sensors 160 canbe in sleep mode when they are not being used. In addition, thecontroller 104 can control the sensors 160 rather than merely collectdata measured by the sensors 160, which allows the controller 104 toserve as an access point rather than a node in the communication networkof the system 100.

The communication network of the system 100 can have any type of networkarchitecture. For example, the communication network of the system 100can be a mesh network. As another example, the communication network ofthe system 100 can be a star network. In any case, the controller 104serves as an access point, which conserves power. When the controller104 includes an energy storage device (e.g., a battery as part of thepower module 112), even more power can be conserved in the operation ofthe system 100. In addition, using the time-synchronized communicationprotocols 132 described herein, the data transferred between thecontroller 104 and the user 150, the network manager 180, and thesensors 160 is secure.

The communication module 108 of the controller 104 determines andimplements the communication protocol (e.g., from the communicationprotocols 132 of the storage repository 130) that is used when thecontrol engine 106 communicates with (e.g., sends signals to, receivessignals from) the user 150, the network manager 180, and/or one or moreof the sensors 160. In some cases, the communication module 108 accessesthe sensor data 134 to determine which communication protocol is withinthe capability of the recipient of a communication sent by the controlengine 106. In addition, the communication module 108 can interpret thecommunication protocol of a communication received by the controller 104so that the control engine 106 can interpret the communication.

The communication module 108 can send data (e.g., communicationprotocols 132, sensor data 134) directly to and/or retrieve datadirectly from the storage repository 130. Alternatively, the controlengine 106 can facilitate the transfer of data between the communicationmodule 108 and the storage repository 130. The communication module 108can also provide encryption to data that is sent by the controller 104and decryption to data that is received by the controller 104. Thecommunication module 108 can also provide one or more of a number ofother services with respect to data sent from and received by thecontroller 104. Such services can include, but are not limited to, datapacket routing information and procedures to follow in the event of datainterruption.

The timer 110 of the controller 104 can track clock time, intervals oftime, an amount of time, and/or any other measure of time. The timer 110can also count the number of occurrences of an event, whether with orwithout respect to time. Alternatively, the control engine 106 canperform the counting function. The timer 110 is able to track multipletime measurements concurrently. The timer 110 can track time periodsbased on an instruction received from the control engine 106, based onan instruction received from the user 150, based on an instructionprogrammed in the software for the controller 104, based on some othercondition or from some other component, or from any combination thereof

The power module 112 of the controller 104 provides power to one or moreother components (e.g., timer 110, control engine 106) of the controller104. In addition, in certain example embodiments, the power module 112can provide power to the power module 140 of the light fixture 102. Thepower module 112 can include one or more of a number of single ormultiple discrete components (e.g., transistor, diode, resistor), and/ora microprocessor. The power module 112 may include a printed circuitboard, upon which the microprocessor and/or one or more discretecomponents are positioned.

The power module 112 can include one or more components (e.g., atransformer, a diode bridge, an inverter, a converter) that receivespower (for example, through an electrical cable) from a source externalto the light fixture 102 and generates power of a type (e.g.,alternating current, direct current) and level (e.g., 12V, 24V, 120V)that can be used by the other components of the controller 104 and/or bythe power module 140. In addition, or in the alternative, the powermodule 112 can be a source of power in itself to provide signals to theother components of the controller 104 and/or the power module 140. Forexample, the power module 112 can be a battery. As another example, thepower module 112 can be a localized photovoltaic power system.

In certain example embodiments, the power module 112 of the controller104 can also provide power and/or control signals, directly orindirectly, to one or more of the sensors 160. In such a case, thecontrol engine 106 can direct the power generated by the power module112 to the sensors 160 and/or the power module 140 of the light fixture102. In this way, power can be conserved by sending power to the sensors160 and/or the power module 140 of the light fixture 102 when thosedevices need power, as determined by the control engine 106.

The hardware processor 120 of the controller 104 executes software inaccordance with one or more example embodiments. Specifically, thehardware processor 120 can execute software on the control engine 106 orany other portion of the controller 104, as well as software used by theuser 150, the network manager 180, and/or one or more of the sensors160. The hardware processor 120 can be an integrated circuit, a centralprocessing unit, a multi-core processing chip, a multi-chip moduleincluding multiple multi-core processing chips, or other hardwareprocessor in one or more example embodiments. The hardware processor 120is known by other names, including but not limited to a computerprocessor, a microprocessor, and a multi-core processor.

In one or more example embodiments, the hardware processor 120 executessoftware instructions stored in memory 122. The memory 122 includes oneor more cache memories, main memory, and/or any other suitable type ofmemory. The memory 122 is discretely located within the controller 104relative to the hardware processor 120 according to some exampleembodiments. In certain configurations, the memory 122 can be integratedwith the hardware processor 120.

In certain example embodiments, the controller 104 does not include ahardware processor 120. In such a case, the controller 104 can include,as an example, one or more field programmable gate arrays (FPGA). UsingFPGAs and/or other similar devices known in the art allows thecontroller 104 (or portions thereof) to be programmable and functionaccording to certain logic rules and thresholds without the use of ahardware processor.

The transceiver 124 of the controller 104 can send and/or receivecontrol and/or communication signals. Specifically, the transceiver 124can be used to transfer data between the controller 104 and the user150, the network manager 180, and/or the sensors 160. The transceiver124 can use wired and/or wireless technology. The transceiver 124 can beconfigured in such a way that the control and/or communication signalssent and/or received by the transceiver 124 can be received and/or sentby another transceiver that is part of the user 150, the network manager180, and/or the sensors 160.

When the transceiver 124 uses wireless technology, any type of wirelesstechnology can be used by the transceiver 124 in sending and receivingsignals. Such wireless technology can include, but is not limited to,Wi-Fi, visible light communication, cellular networking, and Bluetooth.The transceiver 124 can use one or more of any number of suitablecommunication protocols (e.g., ISA100, HART) when sending and/orreceiving signals. Such communication protocols can be stored in thecommunication protocols 132 of the storage repository 130. Further, anytransceiver information for the user 150, the network manager 180,and/or the sensors 160 can be part of the sensor data 134 (or similarareas) of the storage repository 130.

Optionally, in one or more example embodiments, the security module 128secures interactions between the controller 104, the user 150, thenetwork manager 180, and/or the sensors 160. More specifically, thesecurity module 128 authenticates communication from software based onsecurity keys verifying the identity of the source of the communication.For example, user software may be associated with a security keyenabling the software of the user 150 to interact with the controller104 and/or the sensors 160. Further, the security module 128 canrestrict receipt of information, requests for information, and/or accessto information in some example embodiments.

As mentioned above, aside from the controller 104 and its components,the light fixture 102 can include a power module 140, one or more lightfixture components 142, and an optional safety barrier 136. The lightfixture components 142 of the light fixture 102 are devices and/orcomponents typically found in a light fixture to allow the light fixture102 to operate. A light fixture component 142 can be electrical,electronic, mechanical, or any combination thereof. The light fixture102 can have one or more of any number and/or type of light fixturecomponents 142. Examples of such light fixture components 142 caninclude, but are not limited to, a control module, a light source, alight engine, a heat sink, an electrical conductor or electrical cable,a terminal block, a lens, a diffuser, a reflector, an air moving device,a baffle, a dimmer, and a circuit board.

The power module 140 of the light fixture 102 provides power to one ormore of the light fixture components 142. The power module 140 can besubstantially the same as, or different than, the power module 112 ofthe controller 104. The power module 140 can include one or more of anumber of single or multiple discrete components (e.g., transistor,diode, resistor), and/or a microprocessor. The power module 140 mayinclude a printed circuit board, upon which the microprocessor and/orone or more discrete components are positioned.

The power module 140 can include one or more components (e.g., atransformer, a diode bridge, an inverter, a converter) that receivespower (for example, through an electrical cable) from the power module112 of the controller 104 and generates power of a type (e.g.,alternating current, direct current) and level (e.g., 12V, 24V, 120V)that can be used by the light fixture components 142. In addition, or inthe alternative, the power module 140 can receive power from a sourceexternal to the light fixture 102. In addition, or in the alternative,the power module 140 can be a source of power in itself. For example,the power module 140 can be a battery, a localized photovoltaic powersystem, or some other source of independent power.

The optional safety barrier 136 can provide protection (e.g.,overvoltage protection, overcurrent protection) for one or morecomponents of the light fixture 102 when the light fixture 102 islocated in a hazardous environment. For example, the safety barrier 136can limit the amount of power delivered to the power module 112 of thecontroller 104 to reduce the risk of explosion, fire, or other adversecondition that can be caused by high amounts of power in the hazardousenvironment. The safety barrier 136 can often be a required componentwhen the light fixture 102 is located in a hazardous environment. Thesafety barrier 136 can include one or more of a number of single ormultiple discrete components (e.g., capacitor, inductor, transistor,diode, resistor, fuse), and/or a microprocessor.

As stated above, the light fixture 102 can be placed in any of a numberof environments. In such a case, the housing 102 of the light fixture102 can be configured to comply with applicable standards for any of anumber of environments. For example, the light fixture 102 can be ratedas a Division 1 or a Division 2 enclosure under NEC standards.Similarly, any of the sensors 160 or other devices communicably coupledto the light fixture 102 can be configured to comply with applicablestandards for any of a number of environments. For example, a sensor 160can be rated as a Division 1 or a Division 2 enclosure under NECstandards.

FIG. 2 illustrates one embodiment of a computing device 218 thatimplements one or more of the various techniques described herein, andwhich is representative, in whole or in part, of the elements describedherein pursuant to certain exemplary embodiments. Computing device 218is one example of a computing device and is not intended to suggest anylimitation as to scope of use or functionality of the computing deviceand/or its possible architectures. Neither should computing device 218be interpreted as having any dependency or requirement relating to anyone or combination of components illustrated in the example computingdevice 218.

Computing device 218 includes one or more processors or processing units214, one or more memory/storage components 215, one or more input/output(I/O) devices 216, and a bus 217 that allows the various components anddevices to communicate with one another. Bus 217 represents one or moreof any of several types of bus structures, including a memory bus ormemory controller, a peripheral bus, an accelerated graphics port, and aprocessor or local bus using any of a variety of bus architectures. Bus217 includes wired and/or wireless buses.

Memory/storage component 215 represents one or more computer storagemedia. Memory/storage component 215 includes volatile media (such asrandom access memory (RAM)) and/or nonvolatile media (such as read onlymemory (ROM), flash memory, optical disks, magnetic disks, and soforth). Memory/storage component 215 includes fixed media (e.g., RAM,ROM, a fixed hard drive, etc.) as well as removable media (e.g., a Flashmemory drive, a removable hard drive, an optical disk, and so forth).

One or more I/O devices 216 allow a customer, utility, or other user toenter commands and information to computing device 218, and also allowinformation to be presented to the customer, utility, or other userand/or other components or devices. Examples of input devices include,but are not limited to, a keyboard, a cursor control device (e.g., amouse), a microphone, a touchscreen, and a scanner. Examples of outputdevices include, but are not limited to, a display device (e.g., amonitor or projector), speakers, outputs to a lighting network (e.g.,DMX card), a printer, and a network card.

Various techniques are described herein in the general context ofsoftware or program modules. Generally, software includes routines,programs, objects, components, data structures, and so forth thatperform particular tasks or implement particular abstract data types. Animplementation of these modules and techniques are stored on ortransmitted across some form of computer readable media. Computerreadable media is any available non-transitory medium or non-transitorymedia that is accessible by a computing device. By way of example, andnot limitation, computer readable media includes “computer storagemedia”.

“Computer storage media” and “computer readable medium” include volatileand non-volatile, removable and non-removable media implemented in anymethod or technology for storage of information such as computerreadable instructions, data structures, program modules, or other data.Computer storage media include, but are not limited to, computerrecordable media such as RAM, ROM, EEPROM, flash memory or other memorytechnology, CD-ROM, digital versatile disks (DVD) or other opticalstorage, magnetic cassettes, magnetic tape, magnetic disk storage orother magnetic storage devices, or any other medium which is used tostore the desired information and which is accessible by a computer.

The computer device 218 is connected to a network (not shown) (e.g., alocal area network (LAN), a wide area network (WAN) such as theInternet, or any other similar type of network) via a network interfaceconnection (not shown) according to some exemplary embodiments. Thoseskilled in the art will appreciate that many different types of computersystems exist (e.g., desktop computer, a laptop computer, a personalmedia device, a mobile device, such as a cell phone or personal digitalassistant, or any other computing system capable of executing computerreadable instructions), and the aforementioned input and output meanstake other forms, now known or later developed, in other exemplaryembodiments. Generally speaking, the computer system 218 includes atleast the minimal processing, input, and/or output means necessary topractice one or more embodiments.

Further, those skilled in the art will appreciate that one or moreelements of the aforementioned computer device 218 is located at aremote location and connected to the other elements over a network incertain exemplary embodiments. Further, one or more embodiments isimplemented on a distributed system having one or more nodes, where eachportion of the implementation (e.g., control engine 106) is located on adifferent node within the distributed system. In one or moreembodiments, the node corresponds to a computer system. Alternatively,the node corresponds to a processor with associated physical memory insome exemplary embodiments. The node alternatively corresponds to aprocessor with shared memory and/or resources in some exemplaryembodiments.

FIG. 3 shows a system diagram of architecture for a networkcommunication system 300 in accordance with certain example embodiments.Referring to FIGS. 1-3, the system 300 of FIG. 3 includes a networkmanager 380 that is communicably coupled, using communication links 305,to three different light fixtures: Light fixture A 302-1, light fixtureB 302-2, and light fixture C 302-3. In certain example embodiments, alight fixture can be referred to as a “hopper”. Each light fixture inthe system 300 can be configured to be communicably coupled, usingcommunication links 305) to one or more other light fixtures in thesystem 300.

The system 300 also includes a total of six sensors: Sensor A 360-1,sensor B 360-2, sensor C 360-3, sensor D 360-4, sensor E 360-5, andsensor F 360-6. Sensor A 360-1 and sensor B 360-2 are communicablycoupled to light fixture A 302-1 using communication links 305. Sensor C360-3 and sensor D 360-4 are communicably coupled to light fixture B302-2 using communication links 305. Sensor E 360-5 and sensor F 360-6are communicably coupled to light fixture C 302-3 using communicationlinks 305. One of more of the sensors 360 of FIG. 3 can be powered, atleast in part, by a battery. A sensor 360 that is directly communicablycoupled to a light fixture 302 can measure one or more parameters thateffect the operation of the light fixture 302 or that have no effect onthe operation of the light fixture 302.

In other words, network manager 380 in the system 300 of FIG. 3 has nodirect communication with any sensors in the system 300. In certainexample embodiments, the network manager 380 is unaware of the existenceof the sensors 360 or any other devices to which the network manager 380is not directly communicably coupled. In this way, since the number ofdevices to which the network manager 380 can be directly communicablycoupled is limited (e.g., the network manager 380 has only 250 channelsunder a wireless HART communication protocol), the system 300 can beexpanded by allowing one or more example light fixtures 302 to assumedirect communication and control of sensors 360 and other remotedevices.

This differs from network communication systems current known in theart, examples of which are shown in FIGS. 4 and 5. Specifically, FIG. 4shows a network communication system 400 currently known in the art, andFIG. 5 shows a network communication system 500 currently known in theart. Referring to FIGS. 1-5, the system 400 of FIG. 4 includes a networkmanager 480 communicably coupled, using communication links 405, tosensor A 490-1. Sensor A 490-1 is communicably coupled, usingcommunication links 405, to sensor B 490-2. Sensor B 490-2 iscommunicably coupled, using communication links 405, to sensor C 490-3.

In this case, the sensors (sensor A 460-1, sensor B 460-2, sensor C460-3) of FIG. 4 are substantially the same as the example sensors(e.g., sensor 160) described herein, except that the sensors of FIG. 4include one or more of a number of components (such as a controller)that allows the sensor to conduct two-way communication with one or moredevices in the system 400. The system 400 of FIG. 4 does not include alight fixture. Instead, sensor A 490-1 acts as a relay for anycommunication with the network manager 480, and sensor B 490-2 acts as arelay for any communication with the network manager 480 that is notintended solely for sensor A 490-1. As a result, sensor A 490-1 is “on”essentially all the time, consuming a significantly greater amount ofpower relative to the amount of power consumed by sensors in exampleembodiments. Similarly, but to a lesser extent, sensor B 490-2 consumesa greater amount of power relative to the power consumed by sensors inexample embodiments.

The system 500 of FIG. 5 includes a network manager 580 communicablycoupled, using communication links 505, to light source A 592-1. Lightsource A 592-1 is communicably coupled to light source B 592-2 and lightsource C 592-3, and light source B 592-2 and light source C 592-3 arecommunicably coupled, using communication links 505, to light source D592-4. Each light source 592 in FIG. 5 is substantially similar to anexample light fixture (e.g., light fixture 102) described herein, exceptthat the light sources in the system 500 of FIG. 5 do not have acontroller (e.g., controller 104). Thus, since none of the lightfixtures of FIG. 5 include a controller, a light source (e.g., lightsource A 592-1) in FIG. 5 merely acts as a relay for any communicationassociated with the network manager 480. As a result, each of the lightsources in the system 500 of FIG. 5 consumes a significantly greateramount of power relative to the power consumed by the light sources ofsystems in example embodiments. Further, there are no sensors in system500.

FIGS. 6 and 7 show a system diagram of a network communication system inaccordance with certain example embodiments. Specifically, FIG. 6 showsthe network communication system 600 when all components in the system600 are working properly (under normal operating conditions). FIG. 7shows a system 700 with all of the components of the system 600 of FIG.6, except where one of the components is not functioning properly.Referring to FIGS. 1-7, the system 600 of FIG. 6 includes a networkmanager 680 communicably coupled, using communication links 505, tolight fixture A 602-1.

Light fixture A 602-1 is communicably coupled, using communication links605, to light fixture C 602-3. Light fixture C 602-3 is communicablycoupled, using communication links 605, to light fixture B 602-2 andlight fixture D 602-4. Light fixture D 602-4 is communicably coupled,using communication links 605, to sensor A 660-1, sensor B 660-2, andsensor C 660-3. While not shown in FIG. 6, light fixture A 602-1, lightfixture B 602-2, and light fixture C 602-3 can each be communicablycoupled to one or more other sensors during normal operating conditions.

In this example, a number of different devices conserve power. Forexample, sensor A 660-1, sensor B 660-2, and sensor C 660-3 are onlyactive (“on”) when a particular sensor is called upon by a light fixture(in this case, light fixture D 602-4). Thus, if a sensor is powered by abattery, the life of the battery can be significantly longer than thelife of a battery in a sensor (e.g., sensor A 490-1) used in systemscurrently known in the art. In the system 600, the network manager 680communicates with a single light fixture (in this case, light fixture A602-1) for the signal to be received by a sensor (e.g., sensor B 660-2).

As a result, the network manager 680 can communicate with a largernumber of devices in the system 600 because many of the devices in thesystem 600 can be indirectly, as opposed to directly, communicablycoupled to the network manager 680. In other words, a light fixture(e.g., light fixture C 602-3), using an example controller, can controla subnetwork of the system 600. As a result, the network manager 680only needs to send a signal to have a function (read a temperature,detect an amount of light) performed in the system 600. The variouslight fixtures of the system 600, each acting with an examplecontroller, determines which sensor should perform the function andcommands the sensor to perform the function on demand.

The example system 600 of FIG. 6 also is capable of automatedreconfiguration in the event of a loss of a light fixture of othercomponent of the system. For example, the system 700 of FIG. 7 issubstantially the same as the system 600 of FIG. 6, except that lightfixture D 602-4 is out of service. As a result, the sensors (in thiscase, sensor A 660-1, sensor B 660-2, and sensor C 660-3) associatedwith light fixture D 602-4 in the system 600 of FIG. 6, need to becontrolled by and in communication with another light fixture. In thiscase, when light fixture D 602-4 becomes out of service (e.g., losespower, malfunctions), light fixture B 602-2 is instructed to takecontrol of and communicate with sensor A 660-1, sensor B 660-2, andsensor C 660-3.

When light fixture 602-4 is out of service, light fixture B 602-2 can beinstructed to communicate with and control sensor A 660-1, sensor B660-2, and sensor C 660-3 in one or more of a number of ways. Forexample, the light fixture B 602-2 can receive an instruction, directlyor indirectly, from the network manager 680 to communicate with andcontrol sensor A 660-1, sensor B 660-2, and sensor C 660-3. As anotherexample, when light fixture D 602-4 becomes out of service, a signal isautomatically generated to instruct the controller of light fixture B602-2 to establish communication and control with sensor A 660-1, sensorB 660-2, and sensor C 660-3. As yet another example, when one of thesensors (e.g., sensor A 660-1) loses communication with the lightfixture D 602-4, the sensor can send a signal to the light fixture (inthis case, light fixture B 602-2) in closest proximity to the sensor.

The selection of light fixture B 602-2 to assume communication andcontrol of sensor A 660-1, sensor B 660-2, and sensor C 660-3 when lightfixture D 602-4 becomes out of service can be based on one or more of anumber of factors. Such factors can include, but are not limited to,proximity to sensor A 660-1, sensor B 660-2, and sensor C 660-3 relativethe other light fixtures in the network 700, number of sensors alreadyunder control of light fixture B 602-2 relative to the other activelight fixtures in the network 600, the configuration of thecommunication links 605, and a default setting. In certain exampleembodiments, when light fixture D 602-4 returns to service, theconfiguration of the components can return to the system 600 shown inFIG. 6 automatically, by instruction from a user, or based on some otherfactor or event.

FIG. 8 shows a network data frame architecture 800 in accordance withcertain example embodiments. As stated above, in certain exampleembodiments, the network manager is unaware of the existence of thesensors or any other devices to which the network manager is notdirectly communicably coupled. In this way, only the applicationsoftware in a server and the controller in the light fixture is aware ofthe existence of the various sensors communicably coupled to the lightfixture.

Referring to FIGS. 1-8, the network manager can communicate with a lightfixture by generating and sending a data packet (e.g., data packet 880).A data packet can have any of a number of portions. For example, thedata packet 880 of FIG. 8 can include an identification portion 881, amaintenance portion 882, a priority portion 883, a reliability portion884, and a payload portion 885. Each of these portions can be populated(or in some cases, unpopulated) with data. The light fixturecommunicably coupled to the network manager includes a portion 886 ofits controller that has a listing of local sensor IDs 887 and controldata 888 associated with the various sensors communicably coupled to thelight fixture.

When the light fixture receives the data packet, the controller of thelight fixture can perform data mapping 889 to map the data in the datapacket to the communication protocol understood by the sensor. Thiscommunication protocol can be the same as, or different than, thecommunication protocol used between the network manager and the lightfixture. The resulting data packet 890 can be sent by the controller ofthe light fixture to the appropriate sensor.

Like the data packet 880 generated by the network manager, the datapacket 890 can include any of a number of portions. For example, thedata packet 890 of FIG. 8 can include an identification portion 891, amaintenance portion 892, a priority portion 893, a reliability portion894, and a payload portion 895. Each of these portions can be populated(or in some cases, unpopulated) with data. The various portions of thedata packet 890 can be the same as, or different than, the variousportions of the data packet 880. The sensor can receive the data packet890 in the desired format (e.g., HART) and send one or more data packetsback to the light fixture in the same format. Subsequently, the lightfixture can perform data mapping 889 to generate a data packet, usingthe data received from the sensor, and send the resulting data packet tothe network manager. Example embodiments provide for light fixtures usedas an access point in a communication network. Specifically, certainexample embodiments allow for a controller of a light fixture tocommunicate with and control one or more sensors, located external tothe light fixture, within a system. In some cases, example lightfixtures can be located in particular environments (e.g., a hazardousenvironment). In such a case, the light fixture can comply with one ormore applicable standards for that environment. Communication betweenthe example light fixture and other components (e.g., a user, a sensor,a network manager) of the system can be conducted using wired and/orwireless technology.

By controlling the sensors, example embodiments can be used to putsensors in sleep mode when they are not in use. Example embodiments useone or more of a number of time-synchronized protocols for the transferof data between the light fixture and the user, the network manager, andthe sensors. Thus, example embodiments can result in lower power usage,as well as more efficient and secure communication between a lightfixture and associated sensor devices, a user, and/or a network manager.When the light fixture is placed in a hazardous environment, a safetybarrier disposed within the example light fixture can be used to improvesafety practices and help ensure that the light fixture and/or thesensors comply with applicable standards for hazardous environments.

Although embodiments described herein are made with reference to exampleembodiments, it should be appreciated by those skilled in the art thatvarious modifications are well within the scope and spirit of thisdisclosure. Those skilled in the art will appreciate that the exampleembodiments described herein are not limited to any specificallydiscussed application and that the embodiments described herein areillustrative and not restrictive. From the description of the exampleembodiments, equivalents of the elements shown therein will suggestthemselves to those skilled in the art, and ways of constructing otherembodiments using the present disclosure will suggest themselves topractitioners of the art. Therefore, the scope of the exampleembodiments is not limited herein.

What is claimed is:
 1. A light fixture, comprising: a housing comprisingat least one wall that forms a cavity; a controller configured tocontrol and communicate with at least one sensor located outside thehousing; and at least one light fixture component coupled to thecontroller and disposed within the cavity of the housing, wherein thecontroller further controls the at least one light fixture component. 2.The light fixture of claim 1, further comprising: a power moduledisposed within the cavity, wherein the power module provides power tothe controller and the at least one sensor.
 3. The light fixture ofclaim 2, wherein the power module comprises an energy storage device. 4.The light fixture of claim 2, wherein the power module enters a reducedpower mode when the controller is idle.
 5. The light fixture of claim 2,further comprising: an additional power module disposed within thecavity, wherein the additional power module supplies power to the atleast one light fixture component.
 6. The light fixture of claim 1,wherein the controller comprises a wireless transceiver.
 7. The lightfixture of claim 1, wherein the housing meets applicable standards for ahazardous environment.
 8. The light fixture of claim 7, furthercomprising: a safety barrier disposed within the housing, wherein thesafety barrier is coupled to at least one electrical conductor that iscoupled to another device outside the housing.
 9. The light fixture ofclaim 1, wherein the controller comprises: a hardware processor; memorycomprising a plurality of instructions; a control engine that executesthe plurality of instructions on the hardware processor to control andcommunicate with the at least one sensor; and a communication modulecoupled to the control engine, wherein the communication moduletransfers communications between the controller and the at least onesensor located outside the housing.
 10. The light fixture of claim 9,wherein the communication module transfers the communications betweenthe controller and the at least one sensor using at least onetime-synchronized communication protocol.
 11. A controller of a lightfixture, the controller comprising: memory comprising a plurality ofinstructions; a control engine coupled to the memory, wherein thecontroller is configured to send and receive communication signals withat least one sensor based on the plurality of instructions, wherein theat least one sensor is external to the light fixture; and acommunication module coupled to the control engine, wherein thecommunication module is configured to transmit the communication signalsbetween the control engine and the at least one sensor, wherein thecontrol module transmits the communication signals using at least onetime-synchronized communication protocol.
 12. The controller of claim11, wherein the memory and the control engine are disposed within acavity formed by a housing of the light fixture.
 13. The controller ofclaim 11, wherein the control engine further controls a power modulethat provides power to at least one light source of the light fixture.14. An electrical system, comprising: at least one sensor; a lightfixture communicably coupled to the at least one sensor, wherein thelight fixture comprises: a housing comprising at least one wall thatforms a cavity; a controller that controls and communicates with the atleast one sensor; and at least one light fixture component coupled tothe controller and disposed within the cavity of the housing, whereinthe controller further controls the at least one light fixturecomponent, wherein the at least one sensor is located outside thehousing of the light fixture.
 15. The electrical system of claim 14,wherein the controller is an access point with respect to the at leastone sensor.
 16. The electrical system of claim 14, further comprising: anetwork manager communicably coupled to the controller.
 17. Theelectrical system of claim 16, wherein the network manager and thecontroller are part of a mesh communication network.
 18. The electricalsystem of claim 17, wherein network manager detects when the lightfixture becomes unavailable and instructs another light fixture toinitiate communication with the at least one sensor.
 19. The electricalsystem of claim 14, wherein the light fixture and the at least onesensor are located in a hazardous environment.
 20. The electrical systemof claim 14, wherein signals are transferred between the controller andthe at least one sensor using at least one time-synchronized protocol.